我'面临的一个问题与当前正在开发的应用程序。问题是，在启动时的应用程序崩溃时，它在后台一段时间，只有在这种情况下。启动应用程序，而这是打死不会导致死机，从调试器或手机。启动应用程序，而这是在后台约5-10分钟，不会导致崩溃，在调试与否。启动应用程序，而在backgorund约15-20分钟，导致崩溃。在使用调试器异常及断点给了我这个文件：

陷阱线调试器休息，就在同年底前NOP：

我无法找到如何调试这任何线索。

任何帮助将是AP preciated。

编辑：这里是一个崩溃日志的堆栈跟踪（我换成我的设备名设备名称和应用程序的名称，并com.company.myAppName我的公司名称）：

看看这个错误消息。这好像是个断言检查已失败的iOS SDK。

断言没有检查指定块将右侧调度队列中运行。从断言消息和堆栈跟踪， - [UIFetchContentInBackgroundAction sendResponse：] 使用的 dispatch_assert_queue 来检查应用程序code正确使用主队列块。

所以，你最好检查一下你的背景获取code，它应该使用主队列，但你的code是使用全局队列，队列串行或并发队列。

I'am facing an issue with an app currently in development. The problem is that the App crash at launch time when it was in background for a while, and only in that case. Launching the app while it was killed doesn't lead to crash, from debugger or from phone. Launching the app while it was in background for about 5-10 min doesn't lead to crash, while debugging or not. Launching the app while in backgorund for about 15-20 min lead to a crash. Using debugger and breakpoint on exception gave me this file :

The debugger break on the trap line, just before the nop at the end with :

I can't find any clue on how to debug this.

Any help would be appreciated.

EDIT : here is a crash log with the stacktrace (I replaced my device name with DeviceName and the app name and my company name with com.company.myAppName) :

Take a look at this error messages. It seems an assertion check was failed in iOS SDK.

The assertion did check that the specified block would run on the right dispatch queue. From the assertion message and the stack trace, -[UIFetchContentInBackgroundAction sendResponse:] uses dispatch_assert_queue to check that the application code are using the main queue for the block properly.

So you'd better check your background fetch code that should use the main queue, but your code is using global queue, serial queue or concurrent queue.

这篇关于如何调试在启动时iOS应用程序崩溃，只有断点汇编文件的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！